Process Modeling for Business Analysts Made Easy: Determining Business Requirements without Pain by Trond Frantzen

Author:Trond Frantzen [Frantzen, Trond]
Language: eng
Format: epub
Publisher: PowerStart Group
Published: 2017-02-06T08:00:00+00:00

Process Modeling for Business Analysts Made Easy 

102

Business rules should be written as simple, single-

subject declarative statements. This helps the reader

understand exactly what we mean when we document

the rules, and we never have to rely on someone else’s

comprehension of the language or their intuitive

understanding.

The ‘BRT Questions’ we ask our clients solicit clear,

unambiguous answers, which can only be “yes,” “no”

or “sometimes” and “maybe” (which we’ll get to soon).

We use shorthand (e.g., 0, 1, or N) to note our clients’

answers, and we call this shorthand multiplicity or

cardinality or, the ratio of occurrences between the

anchor Object and its intersecting Objects. The ratio of

occurrences that’s entered in the cell that joins two

Objects indicates how we should write the business

rules.

For example:



If there is a 1 only we write, “must be only one

{OBJECT}” as the business rule statement.



If there is a value of 1, N only we write, “must be

one or more {OBJECTs}” as the business rule

statement.



If there is a value of N only we write, “must be

several {OBJECTs}” as the business rule statement.



If there is a value of 1, N, 0 we write, “must be

one or more {OBJECTs} … unless there are

none”; or we can write “may be several

{OBJECTs} … unless there are none” as the

business rule statement. We can also write two

rules for the 1, N, 0 relationship, such as “may be

one or more {OBJECTs}” …” followed by “may

never be an {OBJECT}…”.

Download

Copyright Disclaimer:
This site does not store any files on its server. We only index and link to content provided by other sites. Please contact the content providers to delete copyright contents if any and email us, we'll remove relevant links or contents immediately.